Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a scheduled run for hermes. #3822

Merged
merged 3 commits into from
Jun 14, 2023
Merged

Add a scheduled run for hermes. #3822

merged 3 commits into from
Jun 14, 2023

Conversation

DimitrisJim
Copy link
Contributor

@DimitrisJim DimitrisJim commented Jun 12, 2023

Description

I believe this should easily cover us. Sets a schedule for every night to run hermes.

closes: #3779

Commit Message / Changelog Entry

chore: add a scheduled run for hermes.

see the guidelines for commit messages. (view raw markdown for examples)


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

@@ -1,5 +1,14 @@
# The Tests / E2E workflow is used to run end-to-end tests on pull requests originating
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes more sense to add the change to run hermes here instead of duplicating all of the workflow

# by a scheduled run or not.
- id: get-relayer
run: |
if [ "${{ github.event_name }}" == "schedule" ]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if the event is schedule we set hermes as the relayer, if not rly is set.

@@ -80,3 +98,4 @@ jobs:
chain-binary: 'simd'
# on regular PRs we won't run interchain account or upgrade tests.
test-exclusions: 'TestInterTxTestSuite,TestIncentivizedInterTxTestSuite,TestUpgradeTestSuite'
relayer-tag: "${{ needs.determine-image-tag.outputs.relayer }}"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pass as input to the workflow.

Copy link
Contributor

@chatton chatton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Seems like a nice short term solution to be able to run both relayers 👍

Copy link
Member

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A slack notification to a dedicated channel via webhook would be nice💡

@chatton
Copy link
Contributor

chatton commented Jun 14, 2023

@damiannolan

https://github.com/marketplace/actions/slack-notify

@DimitrisJim
Copy link
Contributor Author

DimitrisJim commented Jun 14, 2023

Yeah, I currently will get notified as the last user to touch the workflow. It might make sense to also include the e2e-upgrade cron job, opened #3841

@damiannolan
Copy link
Member

Opened #3842

@DimitrisJim DimitrisJim merged commit 9772fed into main Jun 14, 2023
@DimitrisJim DimitrisJim deleted the hermes_cron_job branch June 14, 2023 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Running e2es with hermes
3 participants